Skip to content

feat: always pull latest image#1113

Merged
earayu merged 1 commit into
mainfrom
feature/update_readme_compose
Jul 17, 2025
Merged

feat: always pull latest image#1113
earayu merged 1 commit into
mainfrom
feature/update_readme_compose

Conversation

@earayu
Copy link
Copy Markdown
Collaborator

@earayu earayu commented Jul 17, 2025

No description provided.

@earayu earayu requested a review from iziang as a code owner July 17, 2025 03:24
@earayu earayu merged commit 500aa57 into main Jul 17, 2025
7 of 9 checks passed
@earayu earayu deleted the feature/update_readme_compose branch July 17, 2025 03:25
@apecloud-bot apecloud-bot added the size/XS Denotes a PR that changes 0-9 lines. label Jul 17, 2025
Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Docker Compose Command Compatibility Issue

The README now instructs users to run docker-compose up -d --pull always. This command mixes Docker Compose V1 (docker-compose) syntax with the --pull always flag, which is exclusive to Docker Compose V2 (docker compose). This incompatibility causes the command to fail with an "unknown flag" error. Additionally, users with modern Docker installations that only include Docker Compose V2 may encounter a "command not found" error for docker-compose.

README.md#L33-L34

ApeRAG/README.md

Lines 33 to 34 in a698708

cp frontend/deploy/env.local.template frontend/.env
docker-compose up -d --pull always

README-zh.md#L33-L34

ApeRAG/README-zh.md

Lines 33 to 34 in a698708

cp frontend/deploy/env.local.template frontend/.env
docker-compose up -d --pull always

Fix in CursorFix in Web


BugBot free trial expires on July 22, 2025
Learn more in the Cursor dashboard.

Was this report helpful? Give feedback by reacting with 👍 or 👎

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XS Denotes a PR that changes 0-9 lines.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants